Shareware Grab Bag/Shareware Grab Bag.iso/011/wf110.arc/WFILER.DOC

Text File | 1987-10-03 | 44.0 KB | 851 lines

                       WFiler Version 1.10

                    Wide Screen File Manager



                          INTRODUCTION

DESIGN PHILOSOPHY

     WFiler is a full-screen file management utility.  Utilities
of this nature are often called "shells," but in this context the
term is somewhat of a misnomer.  A true DOS shell would replace
the DOS command processor, COMMAND.COM.  At best, the current
crop of "shells" only replace some of the functions of
COMMAND.COM, not COMMAND.COM itself.  They still depend upon
COMMAND.COM to process the commands they issue.  Recognition of
the fact that WFiler is not a true shell has played a part in its
design.  Unlike many "shells,", WFiler does not pretend or intend
to totally isolate the user from the DOS command line.  The
author is a confirmed command-line addict, who normally prefers
to execute commands directly at the DOS prompt.  If a program
(i.e., an "external command") exists that does the job well from
the command-line, there is no need-- for this writer at least--to
load up another program just so one can execute that command by
pushing a single key.  Too many DOS "shells" in fact try to
combine two different basic functions into one: (1) directory and
file management, and (2) the ability to execute any and every
program--including applications programms-- without leaving the
host program.

     These biases strongly influence WFiler's design.  The
philosophy behind WFiler is consciously minimalist.  WFiler lacks
the "bells and whistles" that you'll find with "shells" that take
a more expansive approach.  That is not an apology; it is a
warning.  If you want to do it all without ever exiting to DOS,
you'll be disappointed.  So when would you every want to use it?
Basically, the primary rationale for WFiler is to expedite "mass"
file maintenance by presenting you will a full-screen directory
listing that you can visually "tag." Most "shells" do this, of
course, so this alone hardly makes WFiler unique.  But in
designing WFiler, the thought has been to do this well, and to do
little more.  This is reflected, for instance, in WFiler's visual
"look and feel."  Approximately 80 percent of the screen page is
given over to a five-column directory display, in order to
present at one time as many files as possible for tagging.  This
objective as much determines what you don't see as what you do.
You won't see a lot of system statistics, for instance, the time
of day, or other information not essential to the basic task for
which the program was intended.  Neither is there a bar-menu type
of cursor for selecting file operations, as that would futher
clutter up the screen and reduce the space available for the
directory listing.  WFiler's options are sufficiently few, and
accessable through mnemonic key selections, that frequent users
should have no trouble recalling them from memory.  And if your
memory fails, there is a help screen available at the push of F1.


     In keeping with WFiler's objective of expediting mass file
maintenance, it provides for the following mass file operations:
COPY, DELETE, and MOVE.  Of course, once loaded, it would not be
very efficient to have to quit WFiler to do single file
operations, so WFiler provides for certain single file operations
as well: COPY, DELETE, MOVE, and RENAME.  Beyond that, WFiler's
features are few, and features were added during development only
if they significantly complemented the basic task of mass file
maintenance.  Via a "hook" to an external program, explained
below, you can "list" or examine the contents of individual files
as well, which is certainly useful when trying to decide what to
do with a file when you can't remember what it is or does.  In
another effort to expedite mass file maintenance, WFiler will
list the directories of ARC files, and via hooks to external ARC
utilities you can ADD, DELETE, and EXTRACT to and from such
files.  Since the normal environment for WFiler is expected to be
a hard disk, WFiler not only supports hierarchial directory
structures, it also provides two alternative methods for
"navigating" around the directory tree while WFiler is active.
The directory tree feature of WFiler can also be accessed from
the command line on a "stand-alone" basis as a way of navigating
around the disk without loading the entire program.  This feature
was added only because the required code was minimal, and not
because it enhanced the basic functions of WFiler.

     While WFiler is active, you can also shell to DOS (in the
"true" sense of the word, since a second copy of COMMAND.COM is
loaded as a "shell" during this operation).  This feature was
added because it enhances to utility of WFiler without requiring
that every thing you might ever want to do while running WFiler
be anticipated within WFiler's own code.  A good example of the
utility of this feature, for instance, is when the need arises to
format a floppy disk while using WFiler.  If you had to exit
completely, you would lose the current status of any "tags"
assigned during the work session.  With the Shell-to-DOS feature,
you can exit to DOS, format a floppy disk, and return with
WFiler's visual display and internal arrays just as they were
when you left.  Each of WFiler's features, and the mechanics of
WFiler's operation, are discussed in more detail below.

QUICK START

     WFiler is sufficently intuitive that many will be able to
start using it without ever reading the documentation.  But those
who fail to do so will not find all the features of WFiler in
normal working order.  That is because certain features of WFiler
must be "installed" before they will function.  In order to
maintain a little flexibility, WFiler actually as two different
installation routines, each accessable by a different command
line switch.  While this "Quick Start" is intended to explain the
basics of the setup procedures involved, if this explanation
isn't clear enough, just execute the WFSETUP.BAT file that comes
with the distribution archive.  WFSETUP.BAT will automatically
execute WFiler with the command line switches necessary to
invoke the installation routines.

     The first routine will install the directory tree feature of
Wfiler, and is accessed with a "-c" switch from WFiler's command
tail.  In other words, simply type

               C:>wfiler -c <Enter>

at the command line.  You will then be prompted for the complete
path and file name, including the ".com" extension, for the
subdirectory where wfiler will reside.  WFiler has to know where
to find itself because it employs certain cloning procedures to
"patch" itself whenever you use the directory tree feature.  In
essence, it stores a copy of the tree, and your last position
within the tree, in its own code, and it has to be able to find
itself in order to modify this information when required to do
so.

     During the initial installation of the directory tree
feature, WFiler will also read the directory tree.  This will
take a few seconds, of course, depending on the size of the tree
and the speed of the disk.  But once read, the tree is stored in
WFilers internal code, and is loaded each time WFiler is loaded,
without the need to rescan the entire disk.  While this gives
quicker access to the tree for subsequent accesses, it assumes
you do not add or delete directories in the meantime.  If you
ever do, then just "reread" the disk with the "-r" command-line
option.  The difference between "-r" and "-c" is that "-r" only
reads the disk; it does not prompt you for the location where
WFiler will reside.  If you ever want to move Wfiler to another
subdirectory, you will need to rerun the "-c" option in order to
tell WFiler its new location.  During normal operations, the
directory tree is accessed with the backslash ("\") key.  If you
run WFiler before implementing the "-c" installation routine,
will abort directly to that routine the first time you try to
load the tree.

     With Version 1.10, WFiler now supports multiple drives.  How
this affects normal operation is discussed below.  But during the
"-c" installation routine, you will be asked how many drives you
wish to read, and then will be prompted for the drive designators.
If you have two hard disks or a single hard disk partitioned into
two logical drives, say C and D, you should normally respond with
C (presumably the boot drive) first, and then with D.  When reading
multiple trees, WFiler will put the root directory of the first
drive at the top of the queue, but appends the root directory to the
end of the subdirectory listings for subsequent drives.  Since the
subdirectory listings are accessed as a circular queue (explained
in more detail below), this results in the root directories of C
and D (if you only have these two) being listed together in the
directory listing.  If you have a RAM disk as a part of your normal
system setup, there is no reason why it can not be added to the
directory listing.  I have a ram drive set up as E: with no
subdirectories, and enter it after C and D when running the "-c"
setup routine.  You may want to play around with alternative
orders to see what suits you best.

     During the "-c" installation, you will also be asked for the
location and path\filename for COMMAND.COM, the DOS command
processor.  WFiler needs to know this in order to implement the
Shell-to-DOS feature.

     The second installation routine installs the "hooks" to the
external programs used to implement the LIST and ARC functions.
It is accessed with a "-s" switch from WFiler's command tail:

               C:>wfiler -s

You will be prompted for the programs you will use to (1) list and
edit files, and (2) process ARC files.  Again, you must be sure and
include the ".com" (or ".exe") extension when providing the path
and file names for these programs.  The first program you will be
provided for is the program you will use to list files.  I use
Vern Buerg's excellent LIST.COM, and it is the only one that
WFiler has been tested with.  Incidentally, if you use it, and
haven't sent the minimal fee requested to support the program, do
so!

     You will next be prompted for TWO programs to implement the
ARC functions: (1) one to "arc" files, and (2) another to "xarc"
them.  You can use the same program for both, it you like, since
you will be prompted for the necessary command-line switches to
differentiate between the two functions.  But to support Phil
Katz's ARC utilities, PKARC and PKXARC, it is necessary to prompt
for two different programs.  While WFiler allows for a fairly
flexible installation of the ARC functions, it has not been
tested with all possible combinations or versions.  It can not be
guaranteed to handle all possible variations in syntax.  It works
very well with Katz's utilities.  (As a registered user, they are
what the author normally uses).  SEA's ARC Version 5.21 has been
tested, and can be used for both the "arc" and "xarc" functions
merely by selecting the appropriate command-line switch.  Vern
Buerg's ARCE has been used for the "xarc" function.  Buerg's ARCA
has not been tested since it apparently does not duplicate the
normal update process, nor support deletions from the archive.

     With Version 1.10, you may now install a hook to an external
editor.  I have tested this feature only with QEDIT.  It should
work with any editor that can call the file to be edited from
the command line, but if the editor and/or file to be edited
take up too much memory, there may not be enough memory for this
feature to work properly.  I don't use this feature much, and
since WFiler is not intended as a "shell" from which to run normal
editing or word processing sessions, you'll have to decide if and
how you wish to implement this feature.

     Here is a sample "dialogue" of the installation so that you
will know what to expect:

Now enter the full path\name for List.com: c:\ut\su\list62a.com

Now enter a full path\name for Arc: c:\ut\su\pkarc35.com
Command line switch for Arc? <CR>=None: a
Command line switch for Delete? <CR>=None: d
Now enter a full path\name for Xarc: c:\ut\su\pkxarc35.com
Command line switch for Xarc? <CR>=None:

Now enter a full path\name for the Editor: c:\ut\su\q.com
Setup completed.

Note that the .com extensions are supplied.  If you use ARC.EXE,
be sure to supply the .exe extension as well.  Note also the lack
of a "-" or "/" switch prefix when responding to the prompts for
command line switches.  Version 3.5 of the Katz utilities does
not employ such prefixes.  If you use an alternative which does,
be sure to include them.  (E.g., answer "-a" rather than "a" when
prompted for the "Arc" switch).  It is also recommended that you
enter the drive designator as part of the path string so that WFiler
can find these programs if you switch drives during a work session.

     With Version 1.10, all responses to installation prompts default
to the strings previously assigned those variables unless the null
string is considered a valid response (indicated by "<CR>=None").
This means that you can simply skip prompts you do not wish to change
by pressing <Enter>.  But do not do this for queries for which a null
string is a reasonable response (such as the prompt for a switch for
the XARC function) unless that is what you really want.

     That's all there is to it.  At this point, you are ready to
go.  The WFSETUP.BAT file in the distribution archive simply
executes the two commands:

               C:>wfiler -c
               C:>wfiler -s

A final word of caution regarding installation.  You must run the
"-c" routine BEFORE the "-s" routine.  Nothing disasterous will
happen if you don't, but if WFiler does not know where to find
itself, it can not patch itself with the locations for the list
and arc programs you enter during the "-s" installation routine.
The  "-s" routine will terminate with a "Setup Unsuccessful"
message in that instance.  If that happens, just run the "-c"
routine and tell Wfiler where it is!


                            FEATURES

MAIN SCREEN

     When first loaded, WFiler presents the user with a screen
that is divided into two "windows."  Note that WFiler goes
directly to work: there is no intervening logo or pitch for
money.  The upper window contains an 18 line, 5 column wide lower
case directory listing, enough room for 90 files.  If the
directory is larger than that, the excess is stored in successive
"pages" which are accessed through the PgUp and PgDn keys.  The
listing is alphabetized, and in lower case.  The latter reflects
a strong personal preference, and "shells" that only provide for
an upper case listing are an immediate turn-off to this writer.
The only style of alphabetizing that is provided for is the
"default" style.  There are, for instance, no options to provide
for sorting by size or extension.  Maybe in a future release.
However, with Version 1.10 subdirectories are now sorted ahead
of normal file listings, and are not converted to lowercase;
this aids in distinguishing subdirectories from normal files.

     If not in the root directory when first loaded, the first
two entries in the display are "." and "..", with a moveable
"cursor" positioned over the first entry.  These, of course, are
the DOS directory entries for the current directory and the
parent directory, respectively.  The moveable
"cursor" is not the true cursor, but is merely a highlighted area
of the screen that moves as directed by the arrow keys.  Using a
technique I have dubbed "cursor overdrive," the movement of this
"cursor" is fast.  In fact, delays are inserted in the code to
slow it down!  The purpose of "cursor overdrive," and a quirky
side-effect, are discribed more thoroughly in the next paragraph.

     As already implied, cursor movement (dropping the quotes now
that I've explained that it is not the true cursor) is controlled
by the arrow keys.  The cursor moves in all four directions,
wrapping around, or up and down, as necessary.  As the cursor
moves, it changes the "current file" that is displayed in the
bottom window to correspond to the file under the cursor in the
top window.  The bottom window provides complete statistics on
the size, date, time and attribute of the current file.  In order
to speed up cursor movement, the updating of the bottom window is
suspended if you hold the arrow keys down more than momentarily.
Upon sensing the release of the arrow keys, the bottom window
will then be updated to reflect the current file.  However,
because of the nature of the timing loops employed by WFiler to
slow the cursor down so that it is visible, it is conceivably
possible for WFiler to "lose track" of a key release and go into
"permanent cursor overdrive," what some would call "runaway
cursor; in other words, the cursor
continues to move even though you have released the arrow key.

     Normally, this only happens if you hit an arrow key rapidly
several times in staccato fashion, and is easily remedied.  Just press
and release any key and the cursor will stop.  Better yet, if you
are not going to hold the key down, but press and release the key
several times in succession, you can avoid the problem altogether
by pressing the arrow key in somewhat slower and more deliberate
fashion so that WFiler never loses track of your key releases.

     WFiler installs an alternative keyboard interrupt routine in
order to watch for key releases.  In addition to the "runaway
cursor" problem described above, if you use a keyboard utility
that speeds up the keyboard typematic rate, it is possible that
this may also upset WFiler's timing loops, and result in bizarre
cursor behavior.  If you encounter bizarre cursor behavior that
is not solved merely by pressing and releasing a key, and if you
have a cursor speedup routine installed, either uninstall it before
using WFiler, or experiment with reduced typematic rates to see
if that eliminates the problem.

     That just about covers what you need to know about the main
screen.  To recap, you page up and down through the listing (if
it is more than 90 files in length) with the PgUp and PgDn keys,
and you control cursor movement with the arrow keys.  If at any
time you get bored and want to quit, "hit" the ESC key.

     The statistics on display in the bottom window are, for the
most part, self-explanatory.  All of the normal DOS statistics on
the current file are available: filename, size, and the time and
date the file was last accessed.  Also supplied is the status of
the attribute byte, information which the DOS DIR command does
not provide.  WFiler will report the status of most files with
either a "a+" or "a-", depending on the status of the archive
bit.  A "normal" DOS file is one in which all eight bits of the
attribute byte are "off" (binary zero).  This is true only of
files that have been "backed up" and which have the archive bit
turned off.  When a file is created, or opened and modified, the
archive bit is turned on.  WFiler indicates files with archive
bit on, but with all other bits off, as "a+".  A "normal" file
will be reported as having the archive bit off: "a-".  The hidden
system files are reported as "ahrs" (archive bit on, hidden,
read-only, and system bits on also).  Directories are indicated
by ">dir", and other combinations of the attribute bits should be
self-explanatory.  The one exception would be "<del" which does
not refer to the attribute status at all, but which indicates a
file that has been deleted by WFiler (see below).

COLORS

     Version 1.10 of WFiler adds support for colors.  WFiler uses
three pairs of foreground/background attributes to set its colors:
1) normal foreground and background; 2) cursor foreground and
background; and 3) window foreground and background.  The cursor
attributes are also used to set the attributes for all highlighting
used in WFiler's display, such as to highlight the current filename
and statistics, etc.  The window attributes control the colors used
in displaying ARC directories and the directory tree(s).  The
default colors in the distribution copy of WFiler are (1) white on
black for the normal display, (2) black on white (reverse image) for
the cursor and highlighted areas, and (3) white on black for the
windows.

        Alternative colors can be selected by entering "k" or "K"
while running WFiler.  WFiler will then pass control to a patch
routine that will prompt you for alternative color codes.  WFiler
uses the following single letter codes:

        k - black               K - light black (grey)
        b - blue                B - light blue
        g - green               G - light green
        c - cyan                C - light cyan
        r - red                 R - light red
        m - magenta             M - light magenta
        y - dark yellow (brown) Y - yellow
        w - white               W - bright white

When prompted, simply select the single letter code for the color you
wish to assign, and enter it.  Be aware that upper case letters will
set the blink attribute when used as a background color.  As a practical
matter, then, you only have eight background colors to choose from.

        This routine can also be used to control the attributes for a
monochrome monitor.  Following are the valid combinations for monochrome
attributes:
                            Foreground              Background

   Normal                       w                       k
   Intense                      W                       k
   Normal underlined            b                       k
   Intense underlined           B                       k
   Reverse image                k                       w
   Blinking normal              w                       K
   Blinking intense             W                       K
   Blinking normal underlined   b                       K
   Blinking intense underlined  B                       K
   Blinking Reverse image       k                       W

Because WFiler uses the same attributes for highlighting as for the
cursor, the options which set the blinking attribute are not recommended.


NAVIGATION

     Wfiler assumes that its normal environment is a disk with a
hierarchial directory structure (normally hard disk).  It thus
proves two alternative means of moving around the directory tree.
It is important that you understand how these two methods differ
because it affects what you expect to happen when you use
Wfiler's other options.  The first method is to move up and down
the current path with the Grey Plus and Grey Minus keys.  This
type of navigation does NOT change the TRUE current directory,
referred to by WFiler as the "Current Directory." For instance,
when you load WFiler in C:\SYS\DOC, the "Viewing Directory," and
true current directory, are both C:\SYS\DOC.  If you then move up
the path to C:\SYS with the Grey Plus key, the Current Directory
REMAINS C:\SYS\DOC.  WFiler, however, will display the directory
of C:\SYS "as if" it were the current directory, and will tell
you that you are "viewing" C:\SYS.  It is important to keep this
difference straight.  For instance, if you extract a file from an
ARC file in C:\SYS while the Current Directory is C:\SYS\DOC, it
will be extracted to C:\SYS\DOC, not C:\SYS.  This feature is
intentional, and provides a way of getting at other directories
while the true current directory remains unchanged.

     You may move UP the path using this method of navigation at any
time simply by pressing the Grey Plus key.  To move down the path, there
must necessarily be a subdirectory in the current directory to move
down to.  Subdirectories are distinguished from ordinary files by
their attribute.  As noted, with Version 1.10, subdirectories are listed
in capital letters, and are sorted ahead of normal file listings.
As for the attribute for a subdirectory, WFiler reports the
attribute for a directory as ">dir" in the bottom window.  To
move down to a subdirectory, position the cursor over the
directory entry for the subdirectory and press the Grey Minus
key.  That is really all there is to this method of navigation.
But keep in mind where you are: this method of navigation leaves
the true directory unchanged.  You have not really moved up and
down the path at all.  You have just asked WFiler to act as if it
is moving up and down the path.  Note, too, that you can move
laterally--in fact you can move anywhere on the disk--using this
approach, but you will have to move up the path until you come to
a branch that takes you down where you want to go.  Depending on
how you organize your disk, this may only require just a few
keystrokes to go anywhere you want.

     The second method of navigation is to call up WFiler's
Directory Tree feature.  As mentioned in the Quick Start section
above, WFiler retains a copy of the directory tree within its own
code.  You can access this directory tree through a 5-line window
which "pops up" when you enter the backslash "\" key.  No effort
is made to portray the tree visually.  You simply have a 5-line
window on to a "circular queue" in which the current directory is
positioned on the middle (third) line, which is highlighted,
giving the appearance of a static cursor in which the listing
moves in the background.  Pushing the up and down arrows
"rotates" the queue through the window.

     With Version 1.10's support for multiple directories, the way
in which you change directories has been changed.  You can now
change either the Current Directory, the Viewing Directory, or both.
You can also exit without changing either.  Valid key strokes while
viewing the directory tree(s) are:

                C       -  Change the Current Directory
                V       -  Change the Viewing Directory
              <Enter>   -  Change both
               <Esc>    -  Exit with no change

Note that V (the case is insignificant) and <Enter> make the indicated
change and then close the window and return to the Main Screen
automatically.  C does makes the indicated change, but does not close
the window and return to the Main Screen, but remains open in case you
wish to change both C and V, but change them to different directories.
For instance, you may have an ARC file in C:\COMM and you might want to
extract the contents to D:\TEMP.  The ARC program will normally default
to the Current Directory.  If you set D:\TEMP as the current directory
and C:\COMM as the viewing directory, you will not have to type the
target path; WFiler and the ARC program will extract the files from an
archive in C:\COMM to D:\TEMP automatically.

     In order set the current and viewing directories to different
directories, be sure and set the current directory (with "C") first.
If you try and set the viewing directory first, the window will close
and you will have to reopen it with the backslash key.

     The directory tree feature of WFiler can be accessed
directly from the command line, without loading the rest of
WFiler, as a way of changing directories without having to type
the full path.  The command line switch to pull this off is "-t".
In this mode, ESC will exit without changing the current
directory, and <enter> will exit and execute a change to the
directory pointed to by the static cursor.

FILE OPERATIONS

     Now we come to the real reason for WFiler:  mass file
operations.  The key to mass file operations, to coin a phrase,
is "t".  That is the key you enter to "tag" a file as you move
around the screen.  Its opposite is "u" (for "untag," of course).
The "t" and "u" keys are "semi-smart." Up to a point, they will
remember which direction the cursor was moving when last used,
and will advance it in that direction.  Until you come to a
directory entry.  At that point you will have to advance the
cursor "manually" with the arrow keys.  But for that, you could
cursor around the screen with the "t" key and tag every single
file (should you ever think you have the need to do this).
WFiler keeps track of the total number of bytes of files tagged
at the right of the bottom window.

     Three basic file operations, available in BOTH single and
mass modes, are COPY, DELETE and MOVE.  Each operation is
accessed by mnemonic selections of the C, D and M keys in either
unshifted or Alt mode:

          C         --        Single file copy
      Alt-C         --        Mass file copy

          D         --        Single file delete
      Alt-D         --        Mass file delete

          M         --        Single file move
      Alt-M         --        Mass file move

The difference between a "move" and a "copy," for those who may
not know, is that a "move" does not normally copy the source
file; it merely renames it with a new name that reflects the
destination path and file name.  Use "copy" when you want to copy
the file to another drive, or DUPLICATE the file in another
subdirectory of the current drive.  Otherwise, a "move" is
preferable, and is much faster since it does not involve actual
copying, but only renaming.

     With Version 1.10 you can now "move" files across disks.  This
is not a true move in the sense described above, but is simply a
copy+delete operation.  But if you do indeed want to "move" a file
to another disk, you can now do so, and WFiler will perform the
copy+delete operation transparently.

     These operations are safer than their DOS counterparts
(while DOS does not even have a "move" command).  The copy and
move commands check to see if the target file already exists, and
will not overwrite it unless you give them permission.  For
single file copy and move operations, you will be separately
queried for a "destination path" and a "file name." The latter
query gives you the opportunity to assign a different name to the
target.  If you want to leave it unchanged, just type <enter>
when prompted for a file name.

     With Version 1.10, the "default destination" will always be
the current directory.  Thus, if you have your current directory
set to something other than the directory you are viewing, and if
it is the destination for move or copy operations, you may simply
press <Enter> when asked for the destination and WFiler will make
the current directory the destination.  To copy a file from the
viewing directory to a destination equal to the current directory
with the name unchanged only requires two keystrokes: two successive
<Enter> commands.   Mass copies and moves can also be expedited this
way by using the "C" command of the directory tree to set the current
directory to the destination.

     Querying the user during file operations, as well as
reporting the results of file operations, occurs in the bottom
window, which becomes a "dialogue box" for file operations.
WFiler has adequate error handling capabilities, but provides
only minimal reporting when errors are encountered.  For
instance, any error encountered when copying files will result in
an "Error Copying File" message.  The most likely reason for
errors during file operations is operator error, as in entering a
path that doesn't exist.  In this instance, WFiler will signal
that an error occured, but will not prompt you with the
opportunity to create the path the user actually entered.

     At the conclusion of mass copies and moves, WFiler will
query regarding whether or not to remove the tags.  I am amazed
whenever I encounter a program that automatically removes them
after a mass file operation.  Suppose you then want to delete
them, or remove only some of the tags and continue with mass
operations on the rest?  For that reason, removing the tags after
copies and moves is optional.

     Handling tags after a mass delete is a little different.
WFiler returns to the main screen with the tags intact.  You can
always "force" removal of the tags by executing a manual
"refresh" (explained below).  Otherwise, you have to remove the
tags manually by untagging them with the "u" key.  This is a
concession to the author's way of doing things.  Until the
directory is refreshed, deleted files remain in the directory
listing.  But you will be able to tell a deleted file from which
isn't by the attribute flag:  WFiler reports "<del" for files
which are in its listing, but which no longer actually exist.
The size, time and date reports are also blank for deleted files.

     Mass deletes are given special handling as well because they
are potentially the most disasterous of any mass file operations
if you are not careful.  Not only are you queried as to whether
that is really what you want to do, you are given the option of
selectively deleting tagged files.  The prompt you will see is
"<y/s/N>?"  If you respond with a "y" (for "yes"), WFiler will
proceed to delete every tagged file without further user input.
So be sure that is what you really want to do.  If you want to be
safe, respond with a "s" (for "selective delete").  You will then
be queried for each individual delete.  Until you are sure that
WFiler works intuitively FOR YOU, you are strongly encouraged to
take the safe ("s") route.  "N" will abort the process entirely.
But so will any other key, as the affirmative actions ("y" and
"s") will not be performed unless the specific keys required to
implement those actions are pressed.  This holds true for all
file operations.

     At the end of a COPY, MOVE or DELETE operation WFiler pauses
before closing the dialogue window so that you can read any
error messages that may been displayed during the operation.
You will then be prompted to enter the "next key."   WFiler will
pass any valid keystroke directly to the next routine rather than
return to the normal screen display.  For instance, if at the end
of a COPY operation you wish to RENAME the file, entering "R" as
the "next key" will pass control directly to the RENAME routine and
immediately reopen the dialogue box and prompt you for the new name.
If at the end of an operation you press one of the arrow keys,
WFiler will close the dialogue box and automatically advance the
key in the direction you want.  Any key will close the dialogue
box; keys which are valid as WFiler command keys will not only
close the box but will perform the next operation.

     There are three other basic file operations:

               R    --   Rename
           Alt-R    --   Refresh
               L    --   List
               E    --   Edit

Rename works more or less as you would expect.  Although DOS will
handle wildcard renames, WFiler makes no effort to support such
an operation.  The only rename function provided is a single file
function that acts on the current file.

     Refresh re-reads the directory.  In effect, it takes you
back to square one.  It will remove the tags, if present, and
will update the directory listing for any files that have been
deleted.

     List allows you to view or list the current file.  WFiler
does not actually embody any code to list files.  It merely
provides a "hook" for shelling an external program.  (Note that
this involves the loading of a second copy of the command.com
processor, and is thus "shelling" in the true sense of the word).
Although any program which lists text files to the screen should
work, this function has only been tested with Vern Buerg's
unparalleled LIST.COM.  If you try and "<l>ist" a file before
running the "-s" setup routine (see "Quick Start" above), nothing
will happen.  WFiler will not process the "l" keystroke until you
have told it where to find the external program you will use to
provide this feature.

     Like the list feature, editing works via a hook to an external
program of the user's choice.  This feature was added only because
(1) some users requested it, and (2) it only required a few lines of
code.  I have not extensively tested it because I do not consider
editing a normal file maintenance routine, and thus would normally
never use such a feature.

     The final feature under the heading of normal file
operations is the Shell-to-DOS feature.  You can actually shell
to DOS while examining ARC directories (below) as well.  To shell
to DOS, simply enter "s".  You will be instructed to type "EXIT"
to return to WFiler.  A second copy of COMMAND.COM will be loaded
(you will see the IBM and Microsoft logos), and then you will be
presented with your normal DOS prompt.   Be careful not to change
directories while shelled to DOS, or make certain that you
return to the directory you where in when you shelled to DOS before
you exit back to WFiler.

COMMAND LINE OPTIONS

     It is expected that WFiler will normally NOT be executed
with a command tail.  However, WFiler does parse the command line
for two alternative situations.  It first looks for switches.
Valid switches are

               -c        --   clear or install directory tree
               -s        --   install "list" and "arc" programs
               -r        --   read or re-read the directory tree
               -t        --   load the directory tree

Only one switch at a time is valid.  The -c and -s switches will
normally be used only at installation time (see "Quick Start",
above).  Use the -r switch to re-read the directory tree if you
ever add or delete directories.  The -t switch can be used to
access the directory tree as a method of changing directories,
without running the entire program.

     If not a valid switch, then WFiler will assume the command
tail is a path or filename specification.  For instance, if you
are in the \UTIL directory, and want to process files in \WORD,
you can enter

               C:>wfiler \word

and WFiler will load with \UTIL as the "current directory" and
\WORD as the "viewing directory."  Normal DOS wildcard
specifications ("*" and "?") are permissible.   In Version 1.10,
parsing the command line is a little more robust.  If you do
include a drive designator, WFiler assumes the current drive and
adds the drive designator to the string parsed from the command
line.  If you enter the drive designator, but leave off the '\'
for the root directory, WFiler adds it.  There have been other changes
that should be largely transparent to the user.

                          ARC OPTIONS

     WFiler may be unique among "shells" in the degree of
flexibility it provides for managing ARC files.  It does not
implement all ARC options, but it provides sufficient flexibility
to do what this writer considers essential.  First of all, it
will list the directories of ARC files.  The code for this
feature is internal to WFiler, and does not require an external
program.  (However, none of the ARC features work until the "-s"
setup routine has been run.) To list the contents of an ARC file,
simply position the cursor over the ARC file, and press the "a"
key.  Be patient.  It takes a couple of seconds, sometimes
longer, to read the file.  The headers for the files contained in
ARC files are distributed throughout the file, and thus the
entire file must be read.  WFiler does not begin listing any of
the file names until the archive file is completely read.  Once
read, WFiler will "pop up" a 5-line window similar to that used
for the directory tree.  Again, the listing is kept in a
"circular queue." Each line provides three pieces of information
on each file contained in the archive: the file number, the file
name, and the size of the file (its true or uncompressed size).
No effort is made to decode the rest of the headers for files in
the archive (which contains information on the compressed size of
the file, its date and time, and a CRC value).  Since the window
always shows 5 lines, the entries for archives containing less
than 5 files are reported as "<empty>".

     While the archive listing is active, WFiler supports the
following ARC operations

          E    --   Extract single file
          X    --   Extract all files
          D    --   Delete single files
          C    --   Clean current directory

E, X and D all work on files within the ARC file, while Shift-A
and Alt-A work on files in the Viewing Directory.  C is a special
command explained more thoroughly below.

     E extracts the file pointed to by the static cursor on the
middle line of the ARC window.  X extracts all of the files from
the archive.  D deletes the file pointed to by the static cursor
from the archive.  These operations extract the files to the
current directory, so make sure that is where you want them before
proceeding; if not, change the current directory with the "C" option
of the directory tree routine.

     C will "clean" the viewing directory of files archived in a
given archive.  Suppose you have extracted a number of files from
and archive, and no longer want the extract files to clutter up
the directory.  The clean command will delete from the viewing
directory any file with the same name as one found in the archive.
Like the normal mass delete operation, the clean command gives you
the option of proceeding selectively.

     During normal file operations, WFiler supports two archive
operations:

          Shift-A   --   Add single file
           Alt-A    --   Add all tagged files

Shift-A and Alt-A add files to the archive, i.e. files from the
viewing directory to a specified target.  Shift-A adds the
current file, while Alt-A adds all the tagged files.  When these
functions are accessed, the bottom window resumes its "dialogue
box" function and prompts for a target.  The target is passed "as
is" to the arc utility's command line, which means that the
".arc" extension is not required.  Nor must the target be in the
viewing directory, although if not be sure and supply a complete
path when prompted for the arc file name.

                          DISTRIBUTION

     WFiler was written by the author to fulfill a need, and is
hereby offered to anyone who finds that it fulfills similar
needs.  You are free to use this program as you see fit: in its
compiled form Version 1.10 is freely distributable as classic
public domain software.  However, by using it you accept all
liability and responsibility for its use, and absolve the author
of liability and responsibility for any unforeseen or unintended
consequences.

     The author retains copyright over all portions of the source
code not otherwise under copyright, as well as over the visual
display, and this documentation.  Future versions of the program
may or may not be released to the public domain and the author
retains the right to withhold such release of any future version.
Other copyrights as well may pertain to the source code, as noted
below.

                        ACKNOWLEDGEMENTS

     The source code was compiled using the people's compiler,
Turbo Pascal, from Borland.  It makes extensive use of the Mach 2
sub-routine library from MicroHelp, Inc., as well as the library
from Robert Jourdain's book, Turbo Pascal Express.  At the
request of the latter, you are hereby informed that:

     Portions of this software are taken from Turbo Pascal
     Express by Robert Jourdain, and are copyright (c) 1987
     by Robert Jourdain.  They appear in this program by
     permission of the publisher, the Brady division of
     Simon & Schuster, Inc., 1 Gulf+Western Plaza, New York,
     NY 10023.

Helpful hints on programming were provided by Chris Dunford and
Neil Rubenking.  WFiler uses several routines from the Borland
Forum on Compuserve:  Brian Foley's MODIFY.INC, the NUINT9
alternative keyboard interrupt handler, and NEXTFILE.INC.  Don
Strenczewilk supplied an inline procedure for quickly scanning
large arrays.  Version 1.0 was received enthusiastically by many
members of the IBMSW Forum on Compuserve, many of whom made
helpful suggestions on how to improve the program.  My thanks
to all the above.

                (c) 1987 by Basil L. Copeland Jr.

All rights reserved, except as specifically provided for above.
For further information, support, to report bugs, etc., the
author can be contacted on the IBMSW Forum, Compuserve, PPN
71656,472.